Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix using bad base block #78

Merged
merged 1 commit into from
Apr 1, 2020
Merged

Fix using bad base block #78

merged 1 commit into from
Apr 1, 2020

Conversation

loongy
Copy link
Contributor

@loongy loongy commented Apr 1, 2020

This PR fixes #51 by introducing the Rebase.BaseBlocksInRange(begin, end Hash) int in combination with adding Blockchain.LatestBaseBlock. One notable difference from #51 is that we do not do explicit block resynchronisation.

The network assumptions of Tendermint (and therefore Hyperdrive), is that all messages are eventually delivered. This means that we do not need to explicitly resync, because all Proposes will eventually be seen and base blocks will be accepted as part of this. This is a less efficient approach then explicit resynchronisation, so an issue for this has been created and will be implemented in the next release (see #77). It is not implemented for now, because we will be doing an overall review of all data synchronisation to reduce memory allocations and network bandwidth.

@loongy loongy added the bug Something isn't working label Apr 1, 2020
@loongy loongy added this to the v1.3.0 milestone Apr 1, 2020
@loongy loongy self-assigned this Apr 1, 2020
@loongy loongy merged commit 16f7091 into release/1.3.0 Apr 1, 2020
@loongy loongy deleted the fix/bad-base-blocks branch April 1, 2020 02:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant